@snowystinger Yeah Sure, I was waiting to see whether I'm on the right track or not. Will write the test cases :).

Hey @snowystinger, I have added some test cases, feel free to suggest me some more if needed.

A different question is, in TimeField we also see the disabled state but there are no test cases related to them. Is this an issue or we just left them knowingly?

Please direct me with a specific test case and approach that I should have, if I'm not understanding something. @snowystinger

I’d like to add a few considerations, as this PR caught my attention. Currently, for DateField and TimeField I don't see the necessity to keep data props bth in the DateInput and the Corresponding Field component. What is the purpose of this?

In addition, data props such as data-required and data-readonly may need to be added too.

@Persists For data-required and data-readonly, there is already an open issue for that: #6151. I think that can be handled separately in a different PR.

@Persists is this making it difficult to implement something?

Currently, for DateField and TimeField I don't see the necessity to keep data props both in the DateInput and the Corresponding Field component. What is the purpose of this?

Otherwise, it can be useful, particularly when using utility based CSS, to not make selectors that reference parents.

@yihuiliao Thank you!

@snowystinger Thanks! That makes sense.